@BogdanDidenko Thanks the PR, but API and admin need not require the transaction module, because we have neb-light and neb package library, they need not depend on lots of cryptos libraries.

It's bad solution because in all places you have the request structure

tx = {
        "from": options.from,
        "to": options.to,
        "value": utils.toString(options.value),
        "nonce": options.nonce,
        "gasPrice": utils.toString(options.gasPrice),
        "gasLimit": utils.toString(options.gasLimit),
        "contract": options.contract,
        "binary": options.binary
};

And If you change some commands or parameter type on server you should change it in all places. And this approach can have potential problems with backward compatibility and cetera

Yeah, We may need a util or parameter js file to handle the parameters check.

Maybe some validation module with strategies for different types of parameters.

Later We can add the validation module.

Yes. It's not top-priority task.